Read-source requests to support bundled writes in a distributed storage system

ABSTRACT

A method for execution by processing modules of one or more computing devices of a dispersed storage network (DSN), the method begins by identifying a stored data object (using bundled writes) for retrieval from a dispersed storage network (DSN), determining a DSN address that corresponds to the store data object, generating a read source request based on the DSN address, identifying a set of storage units of the DSN, where one or more of the storage units of the set of storage units are associated with storage of the stored data object, sending the read source request to the identified set of storage units, receiving retrieved encoded data slices from at least some of the storage units of the identified set of storage units and dispersed storage error decoding, for each set of encoded data slices, a decode threshold of received encoded data slices to produce a recovered data object.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to 35 U. S.C. § 120, as a continuation-in-part of U.S. Utility patent application Ser. No. 15/671,746, entitled “STORING AND RETRIEVING DATA USING PROXIES,” filed Aug. 8, 2017, which claims priority pursuant to 35 U.S.C. § 120 as a continuation-in-part of U.S. Utility application Ser. No. 14/955,200, entitled “STORING DATA USING A DUAL PATH STORAGE APPROACH” filed Dec. 1, 2015, now issued as U.S. Pat. No. 9,740,547 on Aug. 22, 2017, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/109,700, entitled “REDUNDANTLY STORING DATA IN A DISPERSED STORAGE NETWORK,” filed Jan. 30, 2015, all of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION Technical Field of the Invention

This invention relates generally to computer networks and more particularly to dispersing error encoded data.

Description of Related Art

Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function. For example, Hadoop is an open source software framework that supports distributed applications enabling application execution by thousands of computers.

In addition to cloud computing, a computer may use “cloud storage” as part of its memory system. As is known, cloud storage enables a user, via its computer, to store files, applications, etc. on an Internet storage system. The Internet storage system may include a RAID (redundant array of independent disks) system and/or a dispersed storage system that uses an error correction scheme to encode data for storage.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a dispersed or distributed storage network (DSN) in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the present invention;

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data in accordance with the present invention;

FIG. 4 is a schematic block diagram of a generic example of an error encoding function in accordance with the present invention;

FIG. 5 is a schematic block diagram of a specific example of an error encoding function in accordance with the present invention;

FIG. 6 is a schematic block diagram of an example of a slice name of an encoded data slice (EDS) in accordance with the present invention;

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of data in accordance with the present invention;

FIG. 8 is a schematic block diagram of a generic example of an error decoding function in accordance with the present invention;

FIGS. 9-9A are schematic block diagrams of another embodiment of a dispersed storage network (DSN) in accordance with the present invention;

FIG. 9B is a schematic block diagram of another embodiment of a dispersed storage network (DSN) in accordance with the present invention; and

FIG. 9C is a flowchart illustrating an example of recovering data in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a dispersed, or distributed, storage network (DSN) 10 that includes a plurality of computing devices 12-16, a managing unit 18, an integrity processing unit 20, and a DSN memory 22. The components of the DSN 10 are coupled to a network 24, which may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of storage units 36 that may be located at geographically different sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common site, or a combination thereof. For example, if the DSN memory 22 includes eight storage units 36, each storage unit is located at a different site. As another example, if the DSN memory 22 includes eight storage units 36, all eight storage units are located at the same site. As yet another example, if the DSN memory 22 includes eight storage units 36, a first pair of storage units are at a first common site, a second pair of storage units are at a second common site, a third pair of storage units are at a third common site, and a fourth pair of storage units are at a fourth common site. Note that a DSN memory 22 may include more or less than eight storage units 36. Further note that each storage unit 36 includes a computing core (as shown in FIG. 2, or components thereof) and a plurality of memory devices for storing dispersed error encoded data.

Each of the computing devices 12-16, the managing unit 18, and the integrity processing unit 20 include a computing core 26, which includes network interfaces 30-33. Computing devices 12-16 may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit 18 and the integrity processing unit 20 may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices 12-16 and/or into one or more of the storage units 36.

Each interface 30,32, and 33 includes software and hardware to support one or more communication links via the network 24 indirectly and/or directly. For example, interface 30 supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network 24, etc.) between computing devices 14 and 16. As another example, interface 32 supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network 24) between computing devices 12 & 16 and the DSN memory 22. As yet another example, interface 33 supports a communication link for each of the managing unit 18 and the integrity processing unit 20 to the network 24.

Computing devices 12 and 16 include a dispersed storage (DS) client module 34, which enables the computing device to dispersed storage error encode and decode data as subsequently described with reference to one or more of FIGS. 3-9C. In this example embodiment, computing device 16 functions as a dispersed storage processing agent for computing device 14. In this role, computing device 16 dispersed storage error encodes and decodes data on behalf of computing device 14. With the use of dispersed storage error encoding and decoding, the DSN 10 is tolerant of a significant number of storage unit failures (the number of failures is based on parameters of the dispersed storage error encoding function) without loss of data and without the need for a redundant or backup copies of the data. Further, the DSN 10 stores data for an indefinite period of time without data loss and in a secure manner (e.g., the system is very resistant to unauthorized attempts at accessing the data).

In operation, the managing unit 18 performs DS management services. For example, the managing unit 18 establishes distributed data storage parameters (e.g., vault creation, distributed storage parameters, security parameters, billing information, user profile information, etc.) for computing devices 12-14 individually or as part of a group of user devices. As a specific example, the managing unit 18 coordinates creation of a vault (e.g., a virtual memory block associated with a portion of an overall namespace of the DSN) within the DSTN memory 22 for a user device, a group of devices, or for public access and establishes per vault dispersed storage (DS) error encoding parameters for a vault. The managing unit 18 facilitates storage of DS error encoding parameters for each vault by updating registry information of the DSN 10, where the registry information may be stored in the DSN memory 22, a computing device 12-16, the managing unit 18, and/or the integrity processing unit 20.

The DSN managing unit 18 creates and stores user profile information (e.g., an access control list (ACL)) in local memory and/or within memory of the DSN memory 22. The user profile information includes authentication information, permissions, and/or the security parameters. The security parameters may include encryption/decryption scheme, one or more encryption keys, key generation scheme, and/or data encoding/decoding scheme.

The DSN managing unit 18 creates billing information for a particular user, a user group, a vault access, public vault access, etc. For instance, the DSTN managing unit 18 tracks the number of times a user accesses a non-public vault and/or public vaults, which can be used to generate per-access billing information. In another instance, the DSTN managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate per-data-amount billing information.

As another example, the managing unit 18 performs network operations, network administration, and/or network maintenance. Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module 34) to/from the DSN 10, and/or establishing authentication credentials for the storage units 36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN 10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN 10.

The integrity processing unit 20 performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit 20 performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory 22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSTN memory 22.

FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50, a memory controller 52, main memory 54, a video graphics processing unit 55, an input/output (10) controller 56, a peripheral component interconnect (PCI) interface 58, an 10 interface module 60, at least one 10 device interface module 62, a read only memory (ROM) basic input output system (BIOS) 64, and one or more memory interface modules. The one or more memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66, a host bus adapter (HBA) interface module 68, a network interface module 70, a flash interface module 72, a hard drive interface module 74, and a DSN interface module 76.

The DSN interface module 76 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). The DSN interface module 76 and/or the network interface module 70 may function as one or more of the interface 30-33 of FIG. 1. Note that the 10 device interface module 62 and/or the memory interface modules 66-76 may be collectively or individually referred to as 10 ports.

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data. When a computing device 12 or 16 has data to store it disperse storage error encodes the data in accordance with a dispersed storage error encoding process based on dispersed storage error encoding parameters. The dispersed storage error encoding parameters include an encoding function (e.g., information dispersal algorithm, Reed-Solomon, Cauchy Reed-Solomon, systematic encoding, non-systematic encoding, on-line codes, etc.), a data segmenting protocol (e.g., data segment size, fixed, variable, etc.), and per data segment encoding values. The per data segment encoding values include a total, or pillar width, number (T) of encoded data slices per encoding of a data segment i.e., in a set of encoded data slices); a decode threshold number (D) of encoded data slices of a set of encoded data slices that are needed to recover the data segment; a read threshold number (R) of encoded data slices to indicate a number of encoded data slices per set to be read from storage for decoding of the data segment; and/or a write threshold number (W) to indicate a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. The dispersed storage error encoding parameters may further include slicing information (e.g., the number of encoded data slices that will be created for each data segment) and/or slice security information (e.g., per encoded data slice encryption, compression, integrity checksum, etc.).

In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown in FIG. 4 and a specific example is shown in FIG. 5); the data segmenting protocol is to divide the data object into fixed sized data segments; and the per data segment encoding values include: a pillar width of 5, a decode threshold of 3, a read threshold of 4, and a write threshold of 4. In accordance with the data segmenting protocol, the computing device 12 or 16 divides the data (e.g., a file (e.g., text, video, audio, etc.), a data object, or other data arrangement) into a plurality of fixed sized data segments (e.g., 1 through Y of a fixed size in range of Kilo-bytes to Tera-bytes or more). The number of data segments created is dependent of the size of the data and the data segmenting protocol.

The computing device 12 or 16 then disperse storage error encodes a data segment using the selected encoding function (e.g., Cauchy Reed-Solomon) to produce a set of encoded data slices. FIG. 4 illustrates a generic Cauchy Reed-Solomon encoding function, which includes an encoding matrix (EM), a data matrix (DM), and a coded matrix (CM). The size of the encoding matrix (EM) is dependent on the pillar width number (T) and the decode threshold number (D) of selected per data segment encoding values. To produce the data matrix (DM), the data segment is divided into a plurality of data blocks and the data blocks are arranged into D number of rows with Z data blocks per row. Note that Z is a function of the number of data blocks created from the data segment and the decode threshold number (D). The coded matrix is produced by matrix multiplying the data matrix by the encoding matrix.

FIG. 5 illustrates a specific example of Cauchy Reed-Solomon encoding with a pillar number (T) of five and decode threshold number of three. In this example, a first data segment is divided into twelve data blocks (D1-D12). The coded matrix includes five rows of coded data blocks, where the first row of X11-X14 corresponds to a first encoded data slice (EDS 1_1), the second row of X21-X24 corresponds to a second encoded data slice (EDS 2_1), the third row of X31-X34 corresponds to a third encoded data slice (EDS 3_1), the fourth row of X41-X44 corresponds to a fourth encoded data slice (EDS 4_1), and the fifth row of X51-X54 corresponds to a fifth encoded data slice (EDS 5_1). Note that the second number of the EDS designation corresponds to the data segment number.

Returning to the discussion of FIG. 3, the computing device also creates a slice name (SN) for each encoded data slice (EDS) in the set of encoded data slices. A typical format for a slice name 60 is shown in FIG. 6. As shown, the slice name (SN) 60 includes a pillar number of the encoded data slice (e.g., one of 1-T), a data segment number (e.g., one of 1-Y), a vault identifier (ID), a data object identifier (ID), and may further include revision level information of the encoded data slices. The slice name functions as, at least part of, a DSN address for the encoded data slice for storage and retrieval from the DSN memory 22.

As a result of encoding, the computing device 12 or 16 produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS 1_1 through EDS 5_1 and the first set of slice names includes SN 1_1 through SN 5_1 and the last set of encoded data slices includes EDS 1_Y through EDS 5_Y and the last set of slice names includes SN 1_Y through SN 5_Y.

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of a data object that was dispersed storage error encoded and stored in the example of FIG. 4. In this example, the computing device 12 or 16 retrieves from the storage units at least the decode threshold number of encoded data slices per data segment. As a specific example, the computing device retrieves a read threshold number of encoded data slices.

To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown in FIG. 8. As shown, the decoding function is essentially an inverse of the encoding function of FIG. 4. The coded matrix includes a decode threshold number of rows (e.g., three in this example) and the decoding matrix in an inversion of the encoding matrix that includes the corresponding rows of the coded matrix. For example, if the coded matrix includes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then inverted to produce the decoding matrix.

In one embodiment, “bundled writes” is a technique to achieve improved reliability and at the same time decrease required rebuilding. Bundled writes is an approach that enables more slices to be written then there are available (or performant) dispersed or distributed storage (DS) units. When a DS processing unit determines that some DS units are unavailable, have not confirmed a write, are not keeping up, or otherwise unable to receive slices or receive them in a timely manner, then the DS processing unit can make a determination to apply bundled writes.

When performing a read operation against a system supporting bundled writes, one change is that the read request that indicates a particular slice name to read is no longer adequate in a system supporting bundled writes, as the names for slices which may be present on a particular distributed or dispersed storage (DS) unit can no longer be predicted. While one approach would be to send a width-number of Read-Slice requests to every DS unit, (one request for each possible slice name), this is wasteful in terms of network bandwidth, request serialization and deserialization, process, and IO/seek operations. In one embodiment, to overcome the need to send a width number of read-slice requests to each DS unit, a “Read-Source” request is included, which has a semantic that a DS unit which receives a Read-Source request must return all slices it has whose source name matches the source name provided in the request.

FIGS. 9-9A are schematic block diagrams of another embodiment of a dispersed storage network (DSN) that includes the distributed storage and task (DST) processing unit 16 (computing device) of FIG. 1, the network 24 of FIG. 1, and a DST execution (EX) unit set 440. The DST execution unit set 440 includes a set of DST execution units, where each DST execution unit is affiliated with a unique encoded data slice of a set of encoded data slices for storage where data is dispersed storage error encoded in accordance with dispersal parameters to produce a plurality of sets of encoded data slices. For example, the DST execution unit set includes DST execution units 1-5 when the dispersal parameters include an information dispersal algorithm (IDA) width of n=5. Each DST execution unit may be implemented utilizing the storage unit 36 of FIG. 1.

FIG. 9 illustrates an example operation of storing data using bundled writes, where the DST processing unit 16 dispersed storage error encodes a data object for storage in the DST execution unit set to produce a plurality of sets of encoded data slices, where each encoded data slice of each set of encoded data slices is mapped to a unique DST execution unit of the DST execution unit set in accordance with a slice mapping. For each set of encoded data slices, the DST processing unit 16 identifies an encoded data slice associated with the selected DST execution unit to produce a bundled encoded data slice of a plurality of bundled encoded data slices. For example, the DST processing unit 16 identifies the encoded data slice based on the slice mapping. For instance, the DST processing unit 16 identifies encoded data slices 3-1 through 3-4 corresponding to a third pillar encoded data slice associated with four sets of encoded data slices as the plurality of bundled encoded data slices.

Having produced the bundled encoded data slices, the DST processing unit 16 updates the slice mapping based on the plurality of bundled encoded data slices to produce an updated slice mapping. As a specific example, the DST processing unit 16 selects a distribution approach. The distribution approach maps each bundled encoded data slice of the plurality of bundled encoded data slices to at least one other DST execution unit of the DST execution unit set. The distribution approach includes one or more of even distribution amongst available DST execution units, distribution of more bundled encoded data slices to DST execution units associated with a highest level of performance, and distribution of bundled encoded data slices amongst DST execution units implemented at different sites.

Having updated the slice mapping, the DST processing unit 16 selects a subset of DST execution units of the set of DST execution units for storage of the plurality of bundled encoded data slices in accordance with the updated slice mapping. The selecting may be based on one or more of DST execution unit performance levels, a predetermination, or interpreting system registry information. As a specific example, the DST processing unit 16 determines the updated slice mapping based on the distribution approach. For instance, the DST processing unit 16 maps bundled encoded data slice 3-1 to DST execution unit 1, maps bundled encoded data slice 3-2 to DST execution unit 2, maps bundled encoded data slice 3-3 to DST execution unit 4, and maps bundled encoded data slice 3-4 to DST execution unit 5 when the distribution approach includes the even distribution of the bundled encoded data slices.

Having selected the subset of DST execution units (e.g., DST execution units 1-2, 4-5), the DST processing unit 16, for each DST execution unit of the subset of DST execution units, issues, via the network 24, a write slice request that includes a group of encoded data slices in accordance with the updated slice mapping. For example, the DST processing unit 16 issues, via the network 24, a write slice request 1 that includes encoded data slices 1-1 through 1-4 and bundled encoded data slice 3-1.

FIG. 9A illustrates further steps of the example of operation of the storing of the data where the DST processing unit 16. The DST processing unit 16 facilitates migration of the plurality of bundled encoded data slices from the subset of DST execution units to the selected DST execution unit. As a specific example, each DST execution unit of the subset of DST execution units issues a write slice request to the selected DST execution unit, where the write slice request includes a corresponding bundled encoded data slice. As another specific example, the identified DST execution unit issues read slice requests to the subset of DST execution units and receives read slice responses that includes the plurality of bundled encoded data slices. As another specific example, the DST processing unit 16 issues delete slice requests to the subset of DST execution units to delete the plurality of bundled encoded data slices when confirming that the selected DST execution unit has successfully non-temporarily stored the plurality of bundled encoded data slices.

FIG. 9B is a schematic block diagram of another embodiment of a dispersed storage network (DSN) that includes the distributed storage and task (DST) processing unit 16 (computing device) of FIG. 1, the network 24 of FIG. 1, and a DST execution (EX) unit set 464. The DST execution unit set 464 may be implemented utilizing the DST execution unit set 440 of FIG. 9. The DST execution unit set includes a set of DST execution units, where each DST execution unit is affiliated with a unique encoded data slice of a set of encoded data slices for storage where data is dispersed storage error encoded in accordance with dispersal parameters to produce a plurality of sets of encoded data slices. The stored data is stored at least partially using one or more bundled writes techniques as discussed in FIGS. 9 and 9A. For example, the DST execution unit set 464 includes DST execution units 1-5 when the dispersal parameters include an information dispersal algorithm (IDA) width of n=5. The DSN functions to recover data that has been stored in the DST execution unit set. Each DST execution unit may be implemented utilizing the storage unit(s) 36 of FIG. 1.

In an example of operation of the recovering of the data, the DST processing unit 16 identifies a stored data object for retrieval from the DST execution unit set 464 to produce a data identifier (ID), where the data object is dispersed storage error encoded to produce a plurality of sets of encoded data slices and where the plurality of sets of encoded data slices are stored in the DST execution unit set 464. Each encoded data slice is associated with a unique slice name and each slice name includes a common source name. The identifying includes at least one of interpreting a request and performing a lookup.

Having identified the stored data object for retrieval, the DST processing unit 16 determines a DSN address that corresponds to the stored data object. The DSN address includes a virtual address associated with the storage of the stored data object. The virtual address includes a common source name. As an example of the determining of the DSN address, the DST processing unit 16 interprets an entry of a dispersed hierarchical index based on the data ID to identify the common source name. As another example of the determining of the DSN address, the DST processing unit 16 interprets a DSN directory based on the data ID to identify the common source name.

Having determined the DSN address, the DST processing unit 16 generates a read source request 466 based on the DSN address. For example, the DST processing unit 16 populates a source name field of the read source request 466 with the identified common source name. Having generated the read source request 466, the DST processing unit 16 identifies a set of DST execution units (e.g., of the DST execution unit set). The identifying includes at least one of interpreting a DSN address to physical location table and interpreting DST execution unit status. For instance, the DST processing unit 16 identifies DST execution units 1-5 as the set of DST execution units based on the DSN address to physical location table.

Having identified the set of DST execution units, the DST processing unit 16 sends, via the network 24, the read source request 466 to the identified set of DST execution units. Having sent the read source request 466, the DST processing unit 16 receives, via the network 24, retrieved encoded data slices 468 from at least some of the DST execution units of the identified set of DST execution units.

For each set of encoded data slices, the DST processing unit 16 dispersed storage error decodes a decode threshold number of received encoded data slices to reproduce a data segment corresponding to the set of encoded data slices. Having reproduced the data segment, the DST processing unit 16 aggregates a plurality of reproduced data segments to produce a recovered data object 470.

FIG. 9C is a flowchart illustrating an example of recovering data. The method includes step 476 where a processing module (e.g., of a distributed storage and task (DST) processing unit) identifies a stored data object for retrieval from a dispersed storage network (DSN). The identifying includes at least one of interpreting a request or performing a lookup. The stored data object is stored at least partially using one or more bundled writes techniques as discussed in FIGS. 9 and 9A.

The method continues at step 478 where the processing module determines a DSN address that corresponds to the store data object. The determining includes one or more of interpreting a dispersed hierarchical index, interpreting a DSN directory, or identifying a source name common to all slice names of encoded data slices of the store data object.

The method continues at step 480 where the processing module generates a read source request based on the DSN address. For example, the processing module generates the read source request to include the source name that is common to all slice names of encoded data slices of the store data object.

The method continues at step 482 where the processing module identifies a set of storage units of the DSN, where one or more of the storage units of the set of storage units are associated with storage of the stored data object. The identifying includes one or more of issuing a query, interpreting a query response, interpreting an error message, interpreting a storage unit status, or performing a lookup.

The method continues at step 484 where the processing module sends the read source request to the identified set of storage units. For example, the processing module replicates the read source request and transmits a replicated resource request to each storage unit of the identified set of storage units.

The method continues at step 486 where the processing module receives retrieved encoded data slices from at least some of the storage units of the identified set of storage units. For example, the processing module receives read slice responses and extracts one or more retrieved encoded data slices from the received read slice responses.

For each set of encoded data slices, the method continues at step 488 where the processing module dispersed storage error decodes a decode threshold number of received encoded data slices to produce a recovered data object. For example, for each set of encoded data slices, the processing module identifies a decode threshold number of received encoded data slices dispersed storage error decodes the decode threshold number of encoded data slices to reproduce a data segment of a plurality of data segments of the data object, and aggregates the reproduced plurality of data segments to produce the recovered data object.

The method described above in conjunction with the processing module can alternatively be performed by other modules of the dispersed storage network or by other computing devices. In addition, at least one memory section (e.g., a non-transitory computer readable storage medium) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices of the dispersed storage network (DSN), cause the one or more computing devices to perform any or all of the method steps described above.

It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A method for execution by one or more processing modules of one or more computing devices of a dispersed storage network (DSN), the method comprises: identifying a stored data object for retrieval from a dispersed storage network (DSN), wherein the stored data object is stored at least partially as a bundled write; determining a DSN address that corresponds to the stored data object; generating a read source request based on the DSN address, wherein the read source request includes a common source name; identifying a set of storage units of the DSN, wherein one or more storage units of the set of storage units are associated with the common source name; sending the read source request to the identified set of storage units to retrieve encoded data slices associated with the common source name; receiving the retrieved encoded data slices from at least some of the storage units of the identified set of storage units, wherein each storage unit that receives the read source request returns all stored encoded data slices with a source name that matches the common source name provided in the read source request; and disperse storage error decoding, for each set of the encoded data slices, a decode threshold number of received encoded data slices to produce a recovered data object.
 2. The method of claim 1, wherein the identifying a stored data object for retrieval includes at least one of interpreting a request or performing a lookup.
 3. The method of claim 1, wherein the determining a DSN address includes one or more of interpreting a dispersed hierarchical index, interpreting a DSN directory, or identifying a source name common to all slice names of encoded data slices of the store data object.
 4. The method of claim 1, wherein the generating the read source request includes a source name that is common to all slice names of encoded data slices of the store data object.
 5. The method of claim 1, wherein the identifying a set of storage units of the DSN includes one or more of issuing a query, interpreting a query response, interpreting an error message, interpreting a storage unit status, or performing a lookup.
 6. The method of claim 1, wherein sending the read source request to the identified set of storage units includes replicating the read source request and transmitting a replicated resource request to each storage unit of the identified set of storage units.
 7. The method of claim 1, wherein the receiving the retrieved encoded data slices includes receiving read slice responses and extracting one or more retrieved encoded data slices from the received read slice responses.
 8. The method of claim 1, wherein the dispersed storage error decoding, for each set of encoded data slices, includes identifying a decode threshold number of received encoded data slices, dispersed storage error decoding the decode threshold number of received encoded data slices to reproduce a data segment of a plurality of data segments of the stored data object, and aggregating the received encoded data slices to produce the recovered data object.
 9. A computing device of a group of computing devices of a dispersed storage network (DSN), the computing device comprises: an interface; a local memory; and a processing module operably coupled to the interface and the local memory, wherein the processing module functions to: identify a stored data object for retrieval from a dispersed storage network (DSN), wherein the stored data object is stored at least partially as a bundled write; determine a DSN address that corresponds to the stored data object; generate a read source request based on the DSN address, wherein the read source request includes a common source name; identify a set of storage units of the DSN, wherein one or more storage units of the set of storage units are associated with the common source name; send the read source request to the identified set of storage units to retrieve encoded data slices associated with the common source name; receive the retrieved encoded data slices from at least some of the storage units of the identified set of storage units, wherein each storage unit that receives the read source request returns all stored encoded data slices with a source name that matches the common source name provided in the read source request; and disperse storage error decode, for each set of the encoded data slices, a decode threshold number of received encoded data slices to produce a recovered data object.
 10. The computing device of claim 9, wherein the identify a stored data object for retrieval includes at least one of interpreting a request or performing a lookup.
 11. The computing device of claim 9, wherein the determine a DSN address includes one or more of interpreting a dispersed hierarchical index, interpreting a DSN directory, or identifying a source name common to all slice names of encoded data slices of the stored data object.
 12. The computing device of claim 9, wherein the generate a read source request includes a source name that is common to all slice names of encoded data slices of the stored data object.
 13. The computing device of claim 9, wherein the identify a set of storage units of the DSN includes one or more of issuing a query, interpreting a query response, interpreting an error message, interpreting a storage unit status, or performing a lookup.
 14. The computing device of claim 9, wherein the send the read source request to the identified set of storage units includes replicating the read source request and transmitting a replicated resource request to each storage unit of the identified set of storage units.
 15. The computing device of claim 9, wherein the receive the retrieved encoded data slices includes receiving read slice responses and extracting one or more retrieved encoded data slices from the received read slice responses.
 16. The computing device of claim 9, wherein the disperse storage error decode, for each set of encoded data slices, includes identifying a decode threshold number of received encoded data slices, dispersed storage error decoding the decode threshold number of received encoded data slices to reproduce a data segment of a plurality of data segments of the stored data object, and aggregating the received encoded data slices to produce the recovered data object.
 17. A system, the system comprises: an interface; a local memory; and a processing module operably coupled to the interface and the local memory, wherein the processing module functions to: identify a stored data object for retrieval from a dispersed storage network (DSN), wherein the stored data object is stored at least partially as a bundled write; determine a DSN address that corresponds to the stored data object; generate a read source request based on the DSN address, wherein the read source request includes a common source name; identify a set of storage units of the DSN, wherein one or more storage units of the set of storage units are associated with the common source name; send the read source request to the identified set of storage units to retrieve encoded data slices associated with the common source name; receive the retrieved encoded data slices from at least some of the storage units of the identified set of storage units, wherein each storage unit that receives the read source request returns all stored encoded data slices with a source name that matches the common source name provided in the read source request; and disperse storage error decode, for each set of the encoded data slices, a decode threshold number of received encoded data slices to produce a recovered data object.
 18. The system of claim 17, wherein the determine a DSN address includes one or more of interpreting a dispersed hierarchical index, interpreting a DSN directory, or identifying a source name common to all slice names of encoded data slices of the stored data object.
 19. The system of claim 17, wherein the generate a read source request includes a source name that is common to all slice names of encoded data slices of the stored data object.
 20. The system of claim 17, wherein the send the read source request to the identified set of storage units includes replicating the read source request and transmitting a replicated resource request to each storage unit of the identified set of storage units. 